OhSillyThreatSystem permission errors no longer seen by scripts from DEBUG_CHANNEL. 🔼

Yet one more method of catching them blocked. Pffft

Note that in 0.9.1.1 the suck it and see published way to check does work.

Looks like it was blocking this in 0.9.0.2 as well.

reported=2021-04-22 09:50:32

reporter=onefang

priority=normal

category=Bug

severity=minor

resolution=open

2021-05-05 19:24:16 onefang: OpenSimDefaults.ini has -

[code=ini]

[XEngine]

; Don't include stack traces in silly threat level errors, and don't bother with "OSSL Runtime Error: " either.

; On the other hand, having this true stops the official OpenSim OhSilly detection script from working.

DebuggerSafe = true

[/code]

So might be that.

2021-08-26 12:39:17 onefang: Manually sending stuff to DEBUG_CHANNEL from scripts is still picked up.

Scripts are not picking up the error messages sent to DEBUG_CHANNEL.

SOME errors are being picked up, are they just dropping the OhSilly Threat ones?

[22:47:42] text: The Opensim script functions we are NOT ALLOWED to use -

[22:47:42] 1ring halo: llInstantMessage: An invalid key was passed to llInstantMessage

[22:47:42] text: llInstantMessage: An invalid key was passed to llInstantMessage

1ring halo prim is sending causing those errors, text prim is picking them up.

2021-08-26 13:25:31 onefang: Commit d79d7e228a059e40a9334c9e2ec4c81075443f83 on 2019-10-16 "add OSSL option PermissionErrortoOwner (true or false). if true ossl functions permission errors will only be sent to prim owner, defaul false: send all around"

Might be relevant. Seems to include three different ways of specifying the debug channel, plus I messed with it already.

2021-08-26 16:01:08 onefang: I don't think it's in the sending part, but in the delivery to script part.

Need to dig deeper.